Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Change namespace-wildcard-cert-selector value type from object to string #5933

Merged
merged 1 commit into from
Apr 4, 2024

Conversation

hubwoop
Copy link
Contributor

@hubwoop hubwoop commented Apr 1, 2024

This PR proposes changes the docs on automatic TLS certificate provisioning. In the examples given under "Provisioning certificates per namespace (wildcard certificates)" objects are provided as values for namespace-wildcard-cert-selector, I think only strings can be values for ConfigMap data values. In the next section (Configure config-certmanager ConfigMap) a string is provided.

Proposed Changes

  • ConfigMap's data values can only be of type String

ConfigMap values can only be of type String
Copy link

linux-foundation-easycla bot commented Apr 1, 2024

CLA Signed


The committers listed above are authorized under a signed CLA.

@knative-prow knative-prow bot requested review from csantanapr and skonto April 1, 2024 13:26
Copy link

knative-prow bot commented Apr 1, 2024

Welcome @hubwoop! It looks like this is your first PR to knative/docs 🎉

@knative-prow knative-prow bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 1, 2024
Copy link

netlify bot commented Apr 1, 2024

Deploy Preview for knative ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit f7b7d7c
🔍 Latest deploy log https://app.netlify.com/sites/knative/deploys/660ab5fe6502340008067929
😎 Deploy Preview https://deploy-preview-5933--knative.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@pierDipi
Copy link
Member

pierDipi commented Apr 4, 2024

/cc @ReToCode @skonto @dprotaso

@knative-prow knative-prow bot requested review from dprotaso and ReToCode April 4, 2024 09:38
Copy link
Member

@ReToCode ReToCode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you are right, the existing method does not work. Thanks for the fix.

/lgtm
/approve

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Apr 4, 2024
Copy link

knative-prow bot commented Apr 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hubwoop, ReToCode

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 4, 2024
@knative-prow knative-prow bot merged commit f96487d into knative:main Apr 4, 2024
19 checks passed
prushh pushed a commit to prushh/docs that referenced this pull request Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants